| <# | |
| .SYNOPSIS | |
| Uninstalls VMware Tools using the MSI installer method. | |
| .DESCRIPTION | |
| This script modifies the VMware Tools MSI database to bypass environment checks | |
| that prevent uninstallation on non-VMware systems, then performs an uninstall. | |
| .PARAMETER Uninstall | |
| Actually perform the uninstall. Without this switch, the script runs in dry-run mode. | |
| .PARAMETER Force | |
| Bypass the confirmation prompt and proceed with uninstallation automatically. |
| <# | |
| .SYNOPSIS | |
| Uninstalls and removes VMware Tools from a Windows system. | |
| .DESCRIPTION | |
| This script first attempts to uninstall VMware Tools using the MSI installer method, | |
| even if the system is no longer running on VMware. It then performs a comprehensive | |
| cleanup by removing registry entries, filesystem folders, services, and devices. | |
| WARNING: If running this script on a system that has been migrated to a different | |
| hypervisor (e.g., Proxmox with VirtIO drivers), removing VMware storage drivers may |
| <# | |
| .SYNOPSIS | |
| Removes VMware Tools from a Windows system. | |
| .DESCRIPTION | |
| This script removes VMware Tools from a Windows system by deleting registry entries, | |
| filesystem folders, and stopping/removing associated services. | |
| .PARAMETER Force | |
| Bypass the confirmation prompt and proceed with removal automatically. | |
| .EXAMPLE | |
| .\Remove-VMwareTools.ps1 |
| <# | |
| .SYNOPSIS | |
| Uninstalls and removes VMware Tools from remote Windows systems. | |
| .DESCRIPTION | |
| This script uses PowerShell remoting to execute VMware Tools cleanup on one or more | |
| remote computers. It first attempts to uninstall VMware Tools using the MSI installer | |
| method, then performs comprehensive cleanup by removing registry entries, filesystem | |
| folders, services, and devices. | |
| WARNING: If running this script on a system that has been migrated to a different |
February 12, 2026
If you're a developer in China trying to use Claude Code, you've probably hit the 403 wall. This guide covers how to get it working in three scenarios:
claude CLI directly in your terminalclaude CLI inside VS Code's integrated terminal
All packages, except for Tini have been added to termux-root. To install them, simply pkg install root-repo && pkg install docker. This will install the whole docker suite, left only Tini to be compiled manually.
| import requests | |
| import json | |
| import bpy, bmesh | |
| from mathutils import Vector | |
| # Define the API endpoint | |
| URL = "https://api.openf1.org/v1/location" | |
| PARAMS = { | |
| "session_key": 9094, # Example: 2023 Monaco GP | |
| "driver_number": 1, # Example: Driver #1 |
| name | description |
|---|---|
analyze |
Deep analysis of a GitHub PR - checks Jira story completeness, Ruby/SRP best practices, principal engineer feedback, and junior engineer clarity. Use when given a GitHub PR URL to analyze. |
Performs a multi-perspective analysis of a GitHub pull request by launching 5 parallel subagents, then synthesizing their findings into a single cohesive report.
| ## Workflow Orchestration | |
| ### 1. Plan Mode Default | |
| - Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions) | |
| - If something goes sideways, STOP and re-plan immediately | |
| - Don't keep pushing. | |
| - Use plan mode for verification steps, not just building | |
| - Write detailed specs upfront to reduce ambiguity | |
| ### 2. Subagent Strategy |
| ; Please see https://gist.github.com/Jamesits/6a58a1b08d5cd09a94a02f30ddaf0e13#gistcomment-2081294 | |
| ; for instruction. | |
| ; Author: James Swineson <mactype@public.swineson.me> | |
| [General] | |
| Name=James Profile | |
| ; γε―η¨ DirectWrite ζ―ζγ | |
| ; [0:Disable] 1:Enable | |
| DirectWrite=1 |